System and method for active power load management

ABSTRACT

A system for managing consumption of power supplied by an electric utility to power consuming devices includes at least one client device and a server. Each client device operates at least partially responsive to control messages received from the server and controls operation of one or more controllable devices. Each controllable device selectively enables and disables a flow of power to one or more of the consuming devices. The server stores information, on a per client device basis, relating to power consumed by the consuming devices. When a power reduction is requested by the utility, the server selects, based on client device information stored in the database, at least one client device to which to issue a power reduction message that indicates at least one of an amount of power to be reduced and an identification of a controllable device to be instructed to disable a flow of power.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to the field of electrical powerload control systems and more particularly to a method and system foractively controlling power load management for individual customers andoptionally tracking power savings for both the individual customer aswell as the overall electric utility.

2. Description of Related Art

The increased awareness of the impact of carbon emissions from the useof fossil fueled electric generation combined with the increased cost ofproducing peak power during high load conditions has increased the needfor alternative solutions utilizing load control as a mechanism todefer, or in some cases eliminate, the need for the deployment ofadditional generation capacity by electric utilities. Existing electricutilities are pressed for methods to defer or eliminate the need forconstruction of fossil-based electricity generation. Today, a patchworkof systems exist to implement demand response load management programs,whereby various radio subsystems in various frequency bands utilize“one-way” transmit only methods of communication. Under these programs,RF controlled relay switches are typically attached to a customer's airconditioner, water heater, or pool pump. A blanket command is sent outto a specific geographic area whereby all receiving units within therange of the transmitting station (e.g., typically a paging network) areturned off during peak hours at the election of the power utility. Aftera period of time when the peak load has passed, a second blanket commandis sent to turn on those devices that have been turned off.

While tele-metering has been used for the express purpose of reportingenergy usage, no techniques exist for calculating power consumption,carbon gas emissions, sulfur dioxide (SO₂) gas emissions, and/ornitrogen dioxide (NO₂) emissions, and reporting the state of aparticular device under the control of a two-way positive control loadmanagement device. In particular, one way wireless communicationsdevices have been utilized to de-activate electrical appliances, such asheating, ventilation, and air-conditioning (HVAC) units, water heaters,pool pumps, and lighting, from an existing electrical supplier ordistribution partner's network. These devices have typically been usedin combination with wireless paging receivers that receive “on” or “off”commands from a paging transmitter. Additionally, the one-way devicesare typically connected to a serving electrical supplier's controlcenter via landline trunks, or in some cases, microwave transmission tothe paging transmitter. The customer subscribing to the load managementprogram receives a discount for allowing the serving electrical supplier(utility) to connect to their electrical appliances and deactivate thoseappliances during high energy usage periods.

While one-way devices are generally industry standard and relativelyinexpensive to implement, the lack of a return path from the receiver,combined with the lack of information on the actual devices connected tothe receiver, make the system highly inefficient for measuring theactual load shed to the serving utility. While the differential currentdraw is measurable on the serving electric utility's transmission lines,the actual load shed is approximate and the location of the loaddeferral is approximated at the control center of the serving utility.

One exemplary tele-metering system is disclosed in U.S. Pat. No.6,891,838 B1. This patent describes details surrounding a meshcommunication of residential devices and the reporting and control ofthose devices, via WANs, to a computer. The stated design goal in thispatent is to facilitate the “monitoring and control of residentialautomation systems.” This patent does not explain how a serving utilityor customer could actively control the devices to facilitate thereduction of electricity. In contrast, this patent discloses techniquesthat could be utilized for reporting information that is being displayedby the serving utility's power meter (as do many other priorapplications in the field of tele-metering).

An additional exemplary tele-metering system is disclosed in U.S. PatentApplication Publication No. 2005/0240315 A1. The primary purpose of thispublished application is not to control utility loads, but rather “toprovide an improved interactive system for remotely monitoring andestablishing the status of a customer utility load.” A stated goal ofthis publication is to reduce the amount of time utility field personnelhave to spend in the field servicing meters by utilizing wirelesstechnology.

Another prior art system is disclosed in U.S. Pat. No. 6,633,823 B2,which describes, in detail, the use of proprietary hardware to remotelyturn off or turn on devices within a building or residence. Whileinitially this prior art generally describes a system that would assistutilities in managing power load control, the prior art does not containthe unique attributes necessary to construct or implement a completesystem. In particular, this patent is deficient in the areas ofsecurity, load accuracy of a controlled device, and methods disclosinghow a customer utilizing applicable hardware might set parameters, suchas temperature set points, customer preference information, and customeroverrides, within an intelligent algorithm that reduces the probabilityof customer dissatisfaction and service cancellation or churn.

Attempts have been made to bridge the gap between one-way, un-verifiedpower load control management systems and positive control verifiedpower load control management systems. However, until recently,technologies such as smart breakers and command relay devices were notconsidered for use in residential and commercial environments primarilydue to high cost entry points, lack of customer demand, and the cost ofpower generation relative to the cost of implementing load control.

One such gap-bridging attempt is described in U.S. Patent ApplicationPublication No. US 2005/0065742 A1. This publication discloses a systemand method for remote power management using IEEE 802 based wirelesscommunication links. The system disclosed in this publication includesan on-premise processor (OPP), a host processor, and an end device. Thehost processor issues power management commands to the OPP, which inturn relays the commands to the end devices under its management. Whilethe disclosed OPP does provide some intelligence in the power managementsystem, it does not determine which end devices under its control toturn-off during a power reduction event, instead relying on the hostdevice to make such decision. For example, during a power reductionevent, the end device must request permission from the OPP to turn on.The request is forwarded to the host device for a decision on therequest in view of the parameters of the on-going power reduction event.The system also contemplates periodic reading of utility meters by theOPP and storage of the read data in the OPP for later communication tothe host device. The OPP may also include intelligence to indicate tothe host processor that the OPP will not be able to comply with a powerreduction command due to the inability of a load under the OPP's controlto be deactivated. However, neither the host processor nor the OPPdetermine which loads to remove in order to satisfy a power reductioncommand from an electric utility, particularly when the command isissued by one of several utilities under the management of a powermanagement system. Further, neither the host processor nor the OPPtracks or accumulates power saved and/or carbon credits earned on a percustomer or per utility basis for future use by the utility and/orcustomer. Still further, the system of this publication lacks a rewardincentive program to customers based on their participation in the powermanagement system. Still further, the system described in thispublication does not provide for secure communications between the hostprocessor and the OPP, and/or between the OPP and the end device. As aresult, the described system lacks many features that may be necessaryfor a commercially viable implementation.

Therefore, a need exists for a system and method for active power loadmanagement for individual customers that is optionally capable oftracking power savings for the individual customer as well as theelectric utility to thereby overcome the shortcomings of the prior art.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an IP-based active power load managementsystem in accordance with an exemplary embodiment of the presentinvention.

FIG. 2 is a block diagram illustrating an exemplary active load director(ALD) server as shown in the system of FIG. 1.

FIG. 3 is a block diagram illustrating an exemplary active load clientand smart breaker module as shown in the system of FIG. 1.

FIG. 4 is an operational flow diagram illustrating a method forautomatically scheduling service calls in an active power loadmanagement system in accordance with one exemplary embodiment of thepresent invention.

FIG. 5 is an operational flow diagram illustrating a method foractivating new subscribers in an active power load management system inaccordance with another exemplary embodiment of the present invention.

FIG. 6 is an operational flow diagram illustrating a method for managingevents occurring in an active power load management system in accordancewith yet another exemplary embodiment of the present invention.

FIG. 7 is an operational flow diagram illustrating a method for activelyreducing consumed power and tracking power savings on an individualcustomer basis in an active power load management system in accordancewith another exemplary embodiment of the present invention.

FIG. 8 is an operational flow diagram illustrating a method for trackingcumulative power savings of an electric utility in an active power loadmanagement system during a power savings event in accordance with yetanother exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Before describing in detail exemplary embodiments that are in accordancewith the present invention, it should be observed that the embodimentsreside primarily in combinations of apparatus components and processingsteps related to actively managing power loading on an individualsubscriber basis and optionally tracking power savings incurred by bothindividual subscribers and an electric utility. Accordingly, theapparatus and method components have been represented where appropriateby conventional symbols in the drawings, showing only those specificdetails that are pertinent to understanding the embodiments of thepresent invention so as not to obscure the disclosure with details thatwill be readily apparent to those of ordinary skill in the art havingthe benefit of the description herein.

In this document, relational terms, such as “first” and “second,” “top”and “bottom,” and the like, may be used solely to distinguish one entityor element from another entity or element without necessarily requiringor implying any physical or logical relationship or order between suchentities or elements. The terms “comprises,” “comprising,” or any othervariation thereof are intended to cover a non-exclusive inclusion, suchthat a process, method, article, or apparatus that comprises a list ofelements does not include only those elements, but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. The term “plurality of” as used in connectionwith any object or action means two or more of such object or action. Aclaim element proceeded by the article “a” or “an” does not, withoutmore constraints, preclude the existence of additional identicalelements in the process, method, article, or apparatus that includes theelement. Additionally, the term “ZigBee” refers to any wirelesscommunication protocol adopted by the Institute of Electronics &Electrical Engineers (IEEE) according to standard 802.15.4 or anysuccessor standard(s), the term “Wi-Fi” refers to any communicationprotocol adopted by the IEEE under standard 802.11 or any successorstandard(s), the term “WiMax” refers to any communication protocoladopted by the IEEE under standard 802.16 or any successor standard(s),and the term “Bluetooth” refers to any short-range communicationprotocol implementing IEEE standard 802.15.1 or any successorstandard(s).

It will be appreciated that embodiments of the invention describedherein may be comprised of one or more conventional processors andunique stored program instructions that control the one or moreprocessors to implement, in conjunction with certain non-processorcircuits, some, most, or all of the functions for managing power loaddistribution and tracking individual subscriber power consumption andsavings in one or more power load management systems as describedherein. The non-processor circuits may include, but are not limited to,radio receivers, radio transmitters, antennas, modems, signal drivers,clock circuits, power source circuits, relays, meters, smart breakers,current sensors, and user input devices. As such, these functions may beinterpreted as steps of a method to distribute information and controlsignals between devices in a power load management system.Alternatively, some or all functions could be implemented by a statemachine that has no stored program instructions, or in one or moreapplication specific integrated circuits (ASICs), in which each functionor some combinations of functions are implemented as custom logic. Ofcourse, a combination of the two approaches could be used. Thus, methodsand means for these functions have been described herein. Further, it isexpected that one of ordinary skill in the art, notwithstanding possiblysignificant effort and many design choices motivated by, for example,available time, current technology, and economic considerations, whenguided by the concepts and principles disclosed herein, will be readilycapable of generating such software instructions, programs andintegrated circuits (ICs), and appropriately arranging and functionallyintegrating such non-processor circuits, without undue experimentation.

Recently, the IEEE has released improved WiMax wireless standards thathave facilitated the consideration of new technologies to improve theresponse and control of power load control devices employing smartbreaker technologies. Embodiments of the present invention expand uponand enhance prior technologies by, among other things, employing WiMaxor IP-based load control in a system with the ability to monitor, inreal time, the amount of power deferred (or carbon, SO₂, or NO₂eliminated). These improvements allow new options for electric utilitiesto defer or invest in new power generation that is friendlier to theenvironment.

IP-based power management is advantageous over existing systems for manyreasons. For example, positive control allows a system controller toreceive a response from an end device installed at a customer location,which indicates that the actual target device has turned “off” or “on.”Additionally, each equipment identifier is unique and each IP address iseither dynamically assigned when the device is activated (e.g., throughuse of the dynamic host configuration protocol (DHCP)) or staticallyassigned by the serving IP network, thereby providing enhanced securityto protect against an act of random terrorism or sabotage inadvertentlyshutting down power services. Existing power management systems,including those utilizing radio subsystems, do not address securityproblems adequately and thus are more likely susceptible to hostile ormalicious acts.

IP-based systems are also bandwidth or network efficient. For example,IP devices are controlled via the 7-layer Open Systems Interconnection(OSI) model whereby the payload of each packet can contain a message or“change in state” and does not require synchronous communication. Thismethod of transmission allows for very minimum overhead and low datarates on a broadband network. Additionally, IP devices can report manystates, including “no power.” For example, the active load client 300may be implemented with a battery backup mechanism to provide backup orauxiliary power to the active load client 300 when AC power is lost. Inthis case, when battery backup is invoked, the active load client 300can report a “no power” condition. Alternatively, a “no power” conditionmay be assumed if an active load client 300 fails to timely respond to amessage (e.g., a poll or other message) from the ALD server 100,particularly where multiple active load clients 300 in a geographic areafail to timely respond to the ALD server messaging. Because thegeographic location of each customer premises and active load client 300may be known at the time of installation or thereafter (e.g., using GPScoordinates), such network outages maybe located on a per meter basis.

One of the most beneficial advantages of an IP-based power managementsystem, as provided in one embodiment of the present invention, isaccurate reporting of the actual amount of power saved by each customeron an individual basis. Embodiments of the present invention monitor andcalculate precisely how many kilowatts (or carbon credits) are beinggenerated or saved per customer instead of merely providing an estimate.Furthermore, embodiments of the present invention provide means fortracking the actual amount of deferred load and pollutants according togeneration mix, serving utility and geographic area.

Embodiments of the present invention include an exemplary system forsupporting a serving utility or power distributor (e.g., such as amunicipality, electric cooperative, or any other wholesale or retailproducer of electric power), methods for providing continuous, real timeactive power control in the system, and a method for determining howmuch actual load may be controlled at any given time for the purposes ofconservation, alternative power generation and the creation of carbon(and other gaseous emissions) credits.

Additional embodiments of the present invention provide a system thatimplements the exemplary methods through the unique use of loadinformation, location of customers consuming electricity, changes instate of controlled devices, current sensing, customer setpoints/preferences and artificial intelligence (e.g., as implementedthrough software) to optimize the presentation of load available to theserving utility for control.

Generally, the embodiments disclosed in the present invention aredirected towards the real time (active) control of residential andcommercial electrical devices that generally are 240V or less. However,specific features and functions may also be applicable to largercommercial installations that are greater than 240V. The descriptionherein is intended to provide a practical implementation of real timeload management for either voluntary or involuntary participants overlarge geographies and ideally for many serving electrical powerproducers, wholesalers or distributors. The exemplary methods andsystems disclosed in the present invention may be implemented by anindividual utility provider, or a third party monitoring service thattracks and manages power loading for one or more utilities. Thisapplication describes the necessary methods and generally describessoftware subsystems for both a host function (e.g., an active loaddirector (ALD) server) and a companion active load client (ALC).

One embodiment of the present invention controls power distribution fora variety of electric utility companies by actively monitoring theamount of power needed by each utility and supplying the required powerby redirecting power from participating customers. In this embodiment,customers agree to allow the power management system to disable certainpower-consuming devices during peak loading times of the day. Smartbreakers, which have the ability to be switched on or off remotely, areinstalled for specific devices in an electric service control panelaccessed by a known IP address. Alternatively, IP-addressable smartappliances maybe used. The power management system determines the amountof steady-state power each device consumes when turned on and logs theinformation in a database for each subscriber. For example, a currentsensor on each smart appliance or within each smart breaker may measurethe amount of current consumed by each monitored device. An active loadclient then multiplies the amount of current consumed by the operatingvoltage of the device to obtain the power consumption, and transmits thepower consumption to the ALD server. When the serving utility needs morepower than it is currently able to supply, the power load managementsystem automatically adjusts the power distribution by turning offspecific loads on an individual subscriber basis. Because the amount ofpower consumed by each specific load is known, the system can determineprecisely which loads to turn off and tracks the power savings generatedby each customer as a result of this short-term outage.

The present invention can be more readily understood with reference toFIGS. 1-8, in which like reference numerals designate like items. FIG. 1depicts an exemplary IP-based active power load management system 10 inaccordance with one embodiment of the present invention. The exemplarypower management system 10 monitors and manages power distribution viaan active load director (ALD) server 100 connected between one or moreutility control centers (UCCs) 200 (one shown) and one or more activeload clients (ALCs) 300 (one shown). The ALD server 100 may communicatewith the utility control center 200 and each active load client 300either directly or through a network 80 using the Internet Protocol (IP)or any other connection-based protocols. For example, the ALD server 100may communicate using RF systems operating via one or more base stations90 (one shown) using one or more wireless communication protocols, suchas Global System for Mobile communications (GSM), Enhanced Data GSMEnvironment (EDGE), High Speed Packet Access (HSDPA), Time DivisionMultiple Access (TDMA), or Code Division Multiple Access data standards,including CDMA 2000, CDMA Revision A, and CDMA Revision B.Alternatively, or additionally, the ALD server 100 may communicate via adigital subscriber line (DSL) capable connection, cable television basedIP capable connection, or any combination thereof. In the exemplaryembodiment shown in FIG. 1, the ALD server 100 communicates with one ormore active load clients 300 using a combination of traditional IP-basedcommunication (e.g., over a trunked line) to a base station 90 and awireless channel implementing the WiMax protocol for the “last mile”from the base station 90 to the active load client 300.

Each active load client 300 is accessible through a specified address(e.g., IP address) and controls and monitors the state of individualsmart breaker modules or intelligent appliances 60 installed in thebusiness or residence 20 to which the active load client 300 isassociated (e.g., connected or supporting). Each active load client 300is associated with a single residential or commercial customer. In oneembodiment, the active load client 300 communicates with a residentialload center 400 that contains smart breaker modules, which are able toswitch from an “ON” (active) state to an “OFF” (inactive), and viceversa, responsive to signaling from the active load client 300. Smartbreaker modules may include, for example, smart breaker panelsmanufactured by Schneider Electric SA under the trademark “Square D” orEaton Corporation under the trademark “Cutler-Hammer” for installationduring new construction. For retro-fitting existing buildings, smartbreakers having means for individual identification and control may beused. Typically, each smart breaker controls a single appliance (e.g., awasher/dryer 30, a hot water heater 40, an HVAC unit 50, or a pool pump70).

Additionally, the active load client 300 may control individual smartappliances directly (e.g., without communicating with the residentialload center 300) via one or more of a variety of known communicationprotocols (e.g., IP, Broadband over PowerLine (BPL) in its variousforms, including through specifications promulgated or being developedby the HOMEPLUG Powerline Alliance and the IEEE, Ethernet, Bluetooth,ZigBee, Wi-Fi, WiMax, etc.). Typically, a smart appliance 60 includes apower control module (not shown) having communication abilities. Thepower control module is installed in-line with the power supply to theappliance, between the actual appliance and the power source (e.g., thepower control module is plugged into a power outlet at the home orbusiness and the power cord for the appliance is plugged into the powercontrol module). Thus, when the power control module receives a commandto turn off the appliance 60, it disconnects the actual power supplyingthe appliance 60. Alternatively, a smart appliance 60 may include apower control module integrated directly into the appliance, which mayreceive commands and control the operation of the appliance directly(e.g., a smart thermostat may perform such functions as raising orlowering the set temperature, switching an HVAC unit on or off, orswitching a fan on or off).

Referring now to FIG. 2, the ALD server 100 may serve as the primaryinterface to customers, as well as to service personnel. In theexemplary embodiment depicted in FIG. 2, the ALD server 100 includes autility control center (UCC) security interface 102, a UCC commandprocessor 104, a master event manager 106, an ALC manager 108, an ALCsecurity interface 110, an ALC interface 112, a web browser interface114, a customer sign-up application 116, customer personal settings 138,a customer reports application 118, a power savings application 120, anALC diagnostic manager 122, an ALD database 124, a service dispatchmanager 126, a trouble ticket generator 128, a call center manager 130,a carbon savings application 132, a utility P & C database 134, a readmeter application 136, and a security device manager 140.

Using the web browser interface 114, in one embodiment, customersinteract with the ALD server 100 and subscribe to some or all of theservices offered by the power load management system 10 via a customersign-up application 116. In accordance with the customer sign-upapplication 116, the customer specifies customer personal settings 138that contain information relating to the customer and the customer'sresidence or business, and defines the extent of service to which thecustomer wishes to subscribe. Additional details of the customer sign-upapplication 116 are discussed below. Customers may also use the webbrowser interface 114 to access and modify information pertaining totheir existing accounts.

The ALD server 100 also includes a UCC security interface 102 whichprovides security and encryption between the ALD server 100 and autility company's control center 200 to ensure that no third party isable to provide unauthorized directions to the ALD server 100. A UCCcommand processor 104 receives and sends messages between the ALD server100 and the utility control center 200. Similarly, an ALC securityinterface 110 provides security and encryption between the ALD server100 and each active load client 300 on the system 10, ensuring that nothird parties can send directions to, or receive information from, theactive load client 300. The security techniques employed by the ALCsecurity interface 110 and the UCC security interface 102 may includeconventional symmetric key or asymmetric key algorithms, such asWireless Encryption Protocol (WEP), Wi-Fi Protected Access (WPA andWPA2), Advanced Encryption Standard (AES), Pretty Good Privacy (PGP), orproprietary encryption techniques.

In one embodiment, the commands that can be received by the UCC commandprocessor 104 from the electric utility's control center 200 include a“Cut” command, a “How Much” command, an “End Event” command, and a “ReadMeters” command. The “Cut” command instructs the ALD server 100 toreduce a specified amount of power for a specified amount of time. Thespecified amount of power may be an instantaneous amount of power or anaverage amount of power consumed per unit of time. The “Cut” command mayalso optionally indicate general geographic areas or specific locationsfor power load reduction. The “How Much” command requests informationfor the amount of power (e.g., in megawatts) that can be reduced by therequesting utility control center 200. The “End Event” command stops thepresent ALD server 100 transaction. The “Read Meters” command instructsthe ALD server 100 to read the meters for all customers serviced by therequesting utility.

The UCC command processor 104 may send a response to a “How Much”command or an “Event Ended” status confirmation to a utility controlcenter 200. A response to a “How Much” command returns an amount ofpower that can be cut. An “Event Ended” acknowledgement message confirmsthat the present ALD server transaction has ended.

The master event manager 106 maintains the overall status of the powerload activities controlled by the power management system 10. The masterevent manager 106 maintains a separate state for each utility that iscontrolled and tracks the current power usage within each utility. Themaster event manager 106 also tracks the management condition of eachutility (e.g., whether or not each utility is currently being managed).The master event manager 106 receives instructions in the form oftransaction requests from the UCC command processor 104 and routesinstructions to components necessary to complete the requestedtransaction, such as the ALC manager 108 and the power savingsapplication 120.

The ALC manager 108 routes instructions between the ALD server 100 andeach active load client 300 within the system 10 through an ALCinterface 112. For instance, the ALC manager 108 tracks the state ofevery active load client 300 serviced by specified utilities bycommunicating with the active load client 300 through an individual IPaddress. The ALC interface 112 translates instructions (e.g.,transactions) received from the ALC manager 108 into the proper messagestructure understood by the targeted active load client 300 and thensends the message to the active load client 300. Likewise, when the ALCinterface 112 receives messages from an active load client 300, ittranslates the message into a form understood by the ALC manager 108 androutes the translated message to the ALC manager 108.

The ALC manager 108 receives from each active load client 300 that itservices, either periodically or responsive to polling messages sent bythe ALC manager 108, messages containing the present power consumptionand the status (e.g., “ON” or “OFF”) of each device controlled by theactive load client 300. Alternatively, if individual device metering isnot available, then the total power consumption and load managementstatus for the entire active load client 300 may be reported. Theinformation contained in each status message is stored in the ALDdatabase 124 in a record associated with the specified active loadclient 300. The ALD database 124 contains all the information necessaryto manage every customer account and power distribution. In oneembodiment, the ALD database 124 contains customer contact information,such as names, addresses, phone numbers, email addresses, and associatedutility companies for all customers having active load clients 300installed at their residences or businesses, as well as a description ofspecific operating instructions for each managed device (e.g.,IP-addressable smart breaker or appliance), device status, and devicediagnostic history.

There are several types of messages that the ALC manager 108 may receivefrom an active load client 300 and process accordingly. One such messageis a security alert message. A security alert message originates from anoptional security or safety monitoring system installed in the residenceor business and coupled to the active load client 300 (e.g., wirelesslyor via a wired connection). When a security alert message is received,the ALC manager 108 accesses the ALD database 124 to obtain routinginformation for determining where to send the alert, and then sends thealert as directed. For example, the ALD manager 108 may be programmed tosend the alert or another message (e.g., an electronic mail message or apre-recorded voice message) to a security monitoring service companyand/or the owner of the residence or business.

Another message communicated between an active load client 300 and theALC manager 108 is a report trigger message. A report trigger messagealerts the ALD server 100 that a predetermined amount of power has beenconsumed by a specific device monitored by an active load client 300.When a report trigger message is received from an active load client300, the ALC manager 108 logs the information contained in the messagein the ALD database 124 for the customer associated with theinformation-supplying active load client 300. The power consumptioninformation is then used by the ALC manager 108 to determine the activeload client(s) 300 to which to send a power reduction or “Cut” messageduring a power reduction event.

Yet another message exchanged between an active load client 300 and theALC manager 108 is a status response message. A status response messagereports the type and status of each device controlled by the active loadclient 300 to the ALD server 100. When a status response message isreceived from an active load client 300, the ALC manager 108 logs theinformation contained in the message in the ALD database 124.

In one embodiment, upon receiving instructions (e.g., a “Cut”instruction) from the master event manager 106 to reduce powerconsumption for a specified utility, the ALC manager 108 determineswhich active load clients 300 and/or individually controlled devices toswitch to the “OFF” state based upon present power consumption datastored in the ALD database 124. The ALC manager 108 then sends a messageto each selected active load client 300 containing instructions to turnoff all or some of the devices under the active load client's control.

In another embodiment, a power savings application 120 may be optionallyincluded to calculate the total amount of power saved by each utilityduring a power reduction event (referred to herein as a “Cut event”), aswell as the amount of power saved for each customer whose active loadclient 300 reduced the amount of power delivered. The power savingsapplication 120 accesses the data stored in the ALD database 124 foreach customer serviced by a particular utility and stores the totalcumulative power savings (e.g., in megawatts per hour) accumulated byeach utility for each Cut event in which the utility participated as anentry in the utility Power and Carbon (“P&C”) database 134.

In a further embodiment, an optional carbon savings application 132 usesthe information produced by the power savings application 120 todetermine the amount of carbon saved by each utility and by eachcustomer for every Cut event. Carbon savings information (e.g., type offuel that was used to generate power for the customer set that wasincluded in the just completed event, power saved in the prior event,governmental standard calculation rates, and/or other data, such asgeneration mix per serving utility and geography of the customer'slocation and the location of the nearest power source) is stored in theALD database 124 for each active load client 300 (customer) and in theutility P&C database 134 for each utility. The carbon savingsapplication 132 calculates the total equivalent carbon credits saved foreach active load client 300 (customer) and utility participating in theprevious Cut event, and stores the information in the ALD database 124and the utility P&C database 134, respectively.

Additionally, the ALC manager 108 automatically provides for smoothoperation of the entire power load management system 10 by optionallyinteracting with a service dispatch manager 126. For example, when a newcustomer subscribes to participate in the power load management system10, the service dispatch manager 126 is notified of the new subscriptionfrom the customer sign-up application 116. The service dispatch manager126 then sends an activation request to the ALC manager 108. Uponreceiving the activation request from the service dispatch manager 126,the ALC manager 108 may sends a query request for information to the newactive load client 300 and, upon receipt of the information, provides itto the service dispatch manager 126. Additionally, if at anytime the ALCmanager 108 detects that a particular active load client 300 is notfunctioning properly, the ALC manager 108 may send a request for serviceto the service dispatch manager 126 to arrange for a service call tocorrect the problem.

In another embodiment, the service dispatch manager 126 may also receiverequests for service from a call center manager 130 that providessupport to an operations center (not shown), which receives telephonecalls from customers of the power load management system 10. When acustomer calls the operations center to request service, the call centermanager 130 logs the service call in the ALD database 124 and sends a“Service” transaction message to the service dispatch manager 126. Whenthe service call has been completed, the call center manager 130receives a completed notification from the service dispatch manager 126and records the original service call as “closed” in the ALD database124.

In yet another embodiment, the service dispatch manager 126 may alsoinstruct an ALC diagnostic manager 122 to perform a series of diagnostictests for any active load client 300 for which the service dispatchmanager 126 has received a service request. After the ALC diagnosticmanager 122 has performed the diagnostic procedure, it returns theresults to the service dispatch manager 126. The service dispatchmanager 126 then invokes a trouble ticket generator 128 to produce areport (e.g., trouble ticket) that includes information (some of whichwas retrieved by the service dispatch manager 126 from the ALD database124) pertaining to the required service (e.g., customer name, address,any special consideration for accessing the necessary equipment, and theresults of the diagnostic process). A residential customer servicetechnician may then use the information provided in the trouble ticketto select the type of equipment and replacement parts necessary forperforming a service call.

A read meter application 136 may be optionally invoked when the UCCcommand processor 104 receives a “Read Meters” or equivalent commandfrom the utility control center 200. The read meter application 136cycles through the ALD database 124 and sends a read meter message orcommand to each active load client 300, or those active load clients 300specifically identified in the UCC's command, via the ALC manager 108.The information received by the ALC manager 108 from the active loadclient 300 is logged in the ALD database 124 for each customer. When allthe active load client meter information has been received, theinformation is sent to the requesting utility control center 200 using abusiness to business (e.g., ebXML) or other desired protocol.

The optional security device management block 140 includes programinstructions for handling security system messages received by thesecurity interface 110. The security device management block 140includes routing information for all security system messages and mayfurther include messaging options on a per customer or service companybasis. For example, one security service may require an email alert fromthe ALD server 100 upon the occurrence of a security event; whereas,another security service may require that the message sent from thein-building system be passed on by the active load client 300 and theALD server 100 directly to the security service company.

In a further embodiment, the ALD server 100 also includes a customerreports application 118 that generates reports to be sent to individualcustomers detailing the amount of power saved during a previous billingcycle. Each report may contain a cumulative total of power savings overthe prior billing cycle, details of the amount of power saved percontrolled device (e.g., breaker or appliance), power savings fromutility directed events, power savings from customer directed events,devices being managed, total carbon equivalents used and saved duringthe period, and/or specific details for each Cut event in which thecustomer's active load client 300 participated. Customers may alsoreceive incentives and awards for participation in the power loadmanagement system 10 through a customer rewards program 150. Forexample, the utilities or a third party system operator may enter intoagreements with product and/or service providers to offer systemparticipants discounts on products and services offered by the providersbased upon certain participation levels or milestones. The rewardsprogram 150 may be setup in a manner similar to conventional frequentflyer programs in which points are accumulated for power saved (e.g.,one point for each megawatt saved or deferred) and, upon accumulation ofpredetermined levels of points, the customer can select a product orservice discount. Alternatively, a serving utility may offer a customera rate discount for participating in the system 10.

FIG. 3 illustrates a block diagram of an exemplary active load client300 in accordance with one embodiment of the present invention. Thedepicted active load client 300 includes a Linux-based operating system302, a status response generator 304, a smart breaker module controller306, a smart device interface 324, a communications interface 308, asecurity interface 310, an IP-based communication converter 312, adevice control manager 314, a smart breaker (B1-BN) counter manager 316,a report trigger application 318, an IP router 320, a smart meterinterface 322, a security device interface 328, and an IP deviceinterface 330. The active load client 300, in this embodiment, is acomputer or processor-based system located on-site at a customer'sresidence or business. The primary function of the active load client300 is to manage the power load levels of controllable devices locatedat the residence or business, which the active load client 300 overseeson behalf of the customer. In an exemplary embodiment, the softwarerunning on the active load client 300 operates using the Linux embeddedoperating system 302 to manage the hardware and the general softwareenvironment. One skilled in the art will readily recognize that otheroperating systems, such as Microsoft's family of operating systems, MacOS, and Sun OS, among others, may be alternatively used. Additionally,the active load client 300 may include DHCP client functionality toenable the active load client 300 to dynamically request IP addressesfor itself and/or one or more controllable devices 402-412, 420, 460managed thereby from a DHCP server on the host IP network facilitatingcommunications between the active load client 300 and the ALD server100. The active load client 300 may further include router functionalityand maintain a routing table of assigned IP addresses in a memory of theactive load client 300 to facilitate delivery of messages from theactive load client 300 to the controllable devices 402-412, 420, 460.

A communications interface 308 facilitates connectivity between theactive load client 300 and the ALD server 100. Communication between theactive load client 300 and the ALD server 100 may be based on any typeof IP or other connection protocol, including but not limited to, theWiMax protocol. Thus, the communications interface 308 may be a wired orwireless modem, a wireless access point, or other appropriate interface.

A standard IP Layer-3 router 320 routes messages received by thecommunications interface 308 to both the active load client 300 and toany other locally connected device 440. The router 320 determines if areceived message is directed to the active load client 300 and, if so,passes the message to a security interface 310 to be decrypted. Thesecurity interface 310 provides protection for the contents of themessages exchanged between the ALD server 100 and the active load client300. The message content is encrypted and decrypted by the securityinterface 310 using, for example, a symmetric encryption key composed ofa combination of the IP address and GPS data for the active load client300 or any other combination of known information. If the message is notdirected to the active load client 300, then it is passed to the IPdevice interface 330 for delivery to one or more locally connecteddevices 440. For example, the IP router 320 may be programmed to routepower load management system messages as well as conventional Internetmessages. In such a case, the active load client 300 may function as agateway for Internet service supplied to the residence or businessinstead of using separate Internet gateways or routers.

An IP based communication converter 312 opens incoming messages from theALD server 100 and directs them to the appropriate function within theactive load client 300. The converter 312 also receives messages fromvarious active load client 300 functions (e.g., a device control manager314, a status response generator 304, and a report trigger application318), packages the messages in the form expected by the ALD server 100,and then passes them on to the security interface 310 for encryption.

The device control manager 314 processes power management commands forvarious controllable devices logically connected to the active loadclient 300. The devices can be either smart breakers 402-412 or other IPbased devices 420, such as smart appliances with individual controlmodules (not shown). The device control manager 314 also processes“Query Request” or equivalent commands or messages from the ALD server100 by querying a status response generator 304 which maintains the typeand status of each device controlled by the active load client 300, andproviding the statuses to the ALD server 100. The “Query Request”message may include information other than mere status requests, such astemperature set points for thermally controlled devices, time intervalsduring which load control is permitted or prohibited, dates during whichload control is permitted or prohibited, and priorities of devicecontrol (e.g., during a power reduction event, hot water heater and poolpump are turned off before HVAC unit is turned off). If temperature setpoints or other non-status information are included in a “Query Request”message and there is a device attached to the active load client 300that can process the information, the temperature set points or otherinformation are sent to that device 420 via a smart device interface324.

The status response generator 304 receives status messages from the ALDserver 100 and, responsive thereto, polls each controllable device402-412, 420, 460 under the active load client's control to determinewhether the controllable device 402-412, 420, 460 is active and in goodoperational order. Each controllable device 402-412, 420,460 responds tothe polls with operational information (e.g., activity status and/orerror reports) in a status response message. The active load client 300stores the status responses in a memory associated with the statusresponse generator 304 for reference in connection with power reductionevents.

The smart device interface 324 facilitates IP or other address-basedcommunications to individual devices 420 (e.g., smart appliance powercontrol modules) that are attached to the active load client 300. Theconnectivity can be through one of several different types of networks,including but not limited to, BPL, ZigBee, Wi-Fi, Bluetooth, or directEthernet communications. Thus, the smart device interface 324 is a modemadapted for use in or on the network connecting the smart devices 420 tothe active load client 300. The smart device interface 324 also allowsthe device control manager 314 to manage those devices that have thecapability to sense temperature settings and respond to temperaturevariations.

The smart breaker module controller 306 formats, sends, and receivesmessages, including power control instructions, to and from the smartbreaker module 400. In one embodiment, the communications is preferablythrough a BPL connection. In such embodiment, the smart breaker modulecontroller 306 includes a BPL modem and operations software. The smartbreaker module 400 contains individual smart breakers 402-412, whereineach smart breaker 402-412 includes an applicable modem (e.g., a BPLmodem when BPL is the networking technology employed) and is preferablyin-line with power supplied to a single appliance or other device. TheB1-BN counter manager 316 determines and stores real time power usagefor each installed smart breaker 402-412. For example, the countermanager 316 tracks or counts the amount of power used by each smartbreaker 402-412 and stores the counted amounts of power in a memory ofthe active load client 300 associated with the counter manager 316. Whenthe counter for any breaker 402-412 reaches a predetermined limit, thecounter manager 316 provides an identification number corresponding tothe smart breaker 402-412 and the corresponding amount of power (powernumber) to the report trigger application 318. Once the information ispassed to the report trigger application 318, the counter manager 316resets the counter for the applicable breaker 402-412 to zero so thatinformation can once again be collected. The report trigger application318 then creates a reporting message containing identificationinformation for the active load client 300, identification informationfor the particular smart breaker 402-412, and the power number, andsends the report to the IP based communication converter 312 fortransmission to the ALD server 100.

The smart meter interface 322 manages either smart meters 460 thatcommunicate using BPL or a current sensor 452 connected to a traditionalpower meter 450. When the active load client 300 receives a “ReadMeters” command or message from the ALD server 100 and a smart meter 460is attached to the active load client 300, a “Read Meters” command issent to the meter 460 via the smart meter interface 322 (e.g., a BPLmodem). The smart meter interface 322 receives a reply to the “ReadMeters” message from the smart meter 460, formats this information alongwith identification information for the active load client 300, andprovides the formatted message to the IP based communication converter312 for transmission to the ALD server 100.

A security device interface 328 transfers security messages to and fromany attached security device. For example, the security device interface328 maybe coupled by wire or wirelessly to a monitoring or securitysystem that includes motion sensors, mechanical sensors, opticalsensors, electrical sensors, smoke detectors, carbon monoxide detectors,and/or other safety and security monitoring devices. When the monitoringsystem detects a security or safety problem (e.g., break-in, fire,excessive carbon monoxide levels), the monitoring system sends its alarmsignal to the security interface 328, which in turn forwards the alarmsignal to the IP network through the ALD server 100 for delivery to thetarget IP address (e.g., the security monitoring service provider). Thesecurity device interface 328 may also be capable of communicating withthe attached security device through the IP device interface torecognize a notification message from the device that it has lost itsline based telephone connection. Once that notification has beenreceived, an alert message is formatted and sent to the ALD server 100through the IP based communication converter 312.

Operation of the power management system 10 in accordance with exemplaryembodiments will now be described. In one embodiment, customersinitially sign up for power load management services using a webbrowser. Using the web browser, the customer accesses a power managementsystem provider's website through the web browser interface 114 andprovides his or her name and address information, as well as the type ofequipment he or she would like to have controlled by the power loadmanagement system 10 to save energy at peak load times and to accumulatepower savings or carbon credits (which may be used to receive rewardincentives based upon the total amount of power or carbon saved by thecustomer). The customer may also agree to allow management of powerconsumption during non-peak times to sell back excess power to theutility, while simultaneously accumulating power savings or carboncredits.

The customer sign up application 116 creates a database entry for eachcustomer in the ALD database 124. Each customer's contact informationand load management preferences are stored or logged in the database124. For example, the customer may be given several simple options formanaging any number of devices or class of devices, including parametersfor managing the devices (e.g., how long each type of device may beswitched off and/or define hours when the devices may not be switchedoff at all). In particular, the customer may also be able to providespecific parameters for HVAC operations (e.g., set control points forthe HVAC system specifying both the low and high temperature ranges).Additionally, the customer may be given an option of receiving anotification (e.g., an email message, Instant Message, Text Message, orrecorded phone call, or any combination thereof) when a power managementevent occurs. When the customer completes entering data, a “New Service”or equivalent transaction message or command is sent to the servicedispatch manager 126.

FIG. 4 illustrates an exemplary operational flow diagram 500 providingsteps executed by the ALD server 100 (e.g., as part of the servicedispatch manager 126) to manage service requests in the exemplary powerload management system 10, in accordance with one embodiment of thepresent invention. The steps of FIG. 4 are preferably implemented as aset of computer instructions (software) stored in a memory (not shown)of the ALD server 100 and executed by one or more processors (not shown)of the ALD server 100. Pursuant to the logic flow, the service dispatchmanager 126 receives (502) a transaction message or command anddetermines (503) the type of transaction. Upon receiving a “New Service”transaction message, the service dispatch manager 126 schedules (504) aservice person (e.g., technician) to make an initial installation visitto the new customer. The service dispatch manager 126 then notifies(506) the scheduled service person, or dispatcher of service personnel,of an awaiting service call using, for example, email, text messaging,and/or instant messaging notifications.

In one embodiment, responsive to the service call notification, theservice person obtains the new customer's name and address, adescription of the desired service, and a service time from a servicedispatch manager service log. The service person obtains an active loadclient 300, all necessary smart breaker modules 402-412, and allnecessary smart switches to install at the customer location. Theservice person notes any missing information from the customer'sdatabase information (e.g., the devices being controlled, type make andmodel of each device, and any other information the system will need tofunction correctly). The service person installs the active load client300 and smart breakers 402-412 at the new customer's location. A globalpositioning satellite (GPS) device may optionally be used by the serviceperson to determine an accurate geographic location of the new customerbuilding, which will be added to the customer's entry in the ALDdatabase 124 and may be used to create a symmetric encryption key tofacilitate secure communications between the ALD server 100 and theactive load client 300. The physical location of the installed activeload client 300 is also entered into the customer's entry. Smart switchdevices may be installed by the service person or left at the customerlocation for installation by the customer. After the active load client300 has been installed, the service dispatch manager 126 receives (508)a report from the service person, via a service log, indicating that theinstallation is complete. The service dispatch manager 126 then sends(510) an “Update” or equivalent transaction message to the ALC manager108.

Returning to block 503, when a “Service” or similar transaction messageor command is received, the service dispatch manager 126 schedules (512)a service person to make a service call to the specified customer. Theservice dispatch manager 126 then sends (514) a “Diagnose” or similartransaction to the ALC diagnostic manager 122. The ALC diagnosticmanager 122 returns the results of the diagnostic procedure to theservice dispatch manager 126, which then notifies (516) the serviceperson of the service call and provides him or her with the results ofthe diagnostic procedure using a conventional trouble ticket. Theservice person uses the diagnostic procedure results in the troubleticket to select the type of equipment and replacement parts necessaryfor the service call.

FIG. 5 illustrates an exemplary operational flow diagram 600 providingsteps executed by the ALD server 100 (e.g., as part of the ALC manager108) to confirm customer sign-up to the power load management system 10,in accordance with one embodiment of the present invention. The steps ofFIG. 5 are preferably implemented as a set of computer instructions(software) stored in a memory (not shown) of the ALD server 100 andexecuted by one or more processors (not shown) of the ALD server 100. Inaccordance with the logic flow, the ALC manager 108 receives (602) an“Update” or similar transaction message or command from the servicedispatch manager 126 and uses the IP address specified in the “Update”message to send (604) out a “QueryRequest” or similar message or commandto the active load client 300. The “Query Request” message includes alist of devices the ALD server 100 expects to be managed. If thecustomer information input at customer sign-up includes temperature setpoints for one or more load-controllable devices, that information isincluded in the “Query Request” message. The ALC manager 108 receives(606) a query reply containing information about the active load client300 (e.g., current WiMax band being used, operational state (e.g.,functioning or not), setting of all the counters for measuring currentusage (e.g., all are set to zero at initial set up time), status ofdevices being controlled (e.g., either switched to the “on” state or“off” state)). The ALC manager 108 updates (608) the ALD database 124with the latest status information obtained from the active load client300. If the ALC manager 108 detects (610), from the query reply, thatthe active load client 300 is functioning properly, it sets (612) thecustomer state to “active” to allow participation in ALD serveractivities. However, if the ALC manager 108 detects (610) that theactive load client 300 is not functioning properly, it sends (614) a“Service” or similar transaction message or command to the servicedispatch manager 126.

FIG. 6 illustrates an exemplary operational flow diagram 700 providingsteps executed by the ALD server 100 (e.g., as part of the master eventmanager 106) to manage events in the exemplary power load managementsystem 10, in accordance with one embodiment of the present invention.The steps of FIG. 6 are preferably implemented as a set of computerinstructions (software) stored in a memory (not shown) of the ALD server100 and executed by one or more processors (not shown) of the ALD server100. Pursuant to the logic flow, the master event manager 106 tracks(702) current power usage within each utility being managed by the ALDserver 100. When the master event manager 106 receives (704) atransaction message or command from the UCC command processor 104 or theALC manager 108, the master event manager 106 determines (706) the typeof transaction received. Upon receiving a “Cut” transaction from the UCCcommand processor 104 (resulting from a “Cut” command issued by theutility control center 200), the master event manager 106 places (708)the utility in a managed logical state. The master event manager thensends (710) a “Cut” transaction or event message or command to the ALCmanager 108 identifying the amount of power (e.g., in megawatts) thatmust be removed from the power system supplied by the utility. Theamount of power specified for reduction in a “Cut” command maybe aninstantaneous amount of power or an average amount of power per unittime. Finally, the master event manager 106 notifies (711) everycustomer that has chosen to receive a notification (e.g., throughtransmission of an email or other pre-established notificationtechnique) that a power management event is in process.

Returning to block 706, when the master event manager 106 receives a“How Much” or other equivalent power inquiry transaction message orcommand from the UCC command processor 104 (resulting from a “How Much”or equivalent power inquiry command issued by the utility control center200), the master event manager 106 determines (712) the amount of powerthat may be temporarily removed from a particular utility's managedsystem by accessing the current usage information for that utility. Thecurrent usage information is derived, in one embodiment, by aggregatingthe total available load for the serving utility, as determined from thecustomer usage information for the utility stored in the ALD database124, based on the total amount of power that may have to be supplied tothe utility's customers in view of the statuses of each of the activeload clients 300 and their respectively controllable load devices402-412, 420, 460 during the load control interval identified in the“How Much” message.

Each utility may indicate a maximum amount of power or maximumpercentage of power to be reduced during any power reduction event. Suchmaximums or limits may be stored in the utility P&C database 134 of theALD server 100 and downloaded to the master event manager 106. In oneembodiment, the master event manager 106 is programmed to remove adefault one percent (1%) of the utility's current power consumptionduring any particular power management period (e.g., one hour). Inalternative embodiments, the master event manager 106 may be programmedto remove other fixed percentages of current power consumption orvarying percentages of current power consumption based on the currentpower consumption (e.g., 1% when power consumption is at system maximumand 10% when power consumption is at only 50% of system maximum). Basedon the amount of power to be removed, the master event manager 106 sends(710) a “Cut” or equivalent event message to the ALC manager 108indicating the amount of power (e.g., in megawatts) that must be removedfrom the utility's power system (e.g., 1% ofthe current usage), andnotifies (711) all customers that have chosen to receive a notificationthat a power management event is in process. The master event manager106 also sends a response to the utility control center 200 via the UCCcommand processor 104 advising the utility control center 200 as to thequantity of power that can be temporarily reduced by the requestingutility.

Returning once again to block 706, when the master event manager 106receives an “End Event” or equivalent transaction message or commandfrom the UCC command processor 104 (resulting from an “End Event”command issued by the utility control center 200), the master eventmanager 106 sets (714) the state of the current event as “Pending” andsends (716) an “End Event” or equivalent transaction message or commandto the ALC manager 108. When the ALC manager 108 has performed the stepsnecessary to end the present event (e.g., a power reduction or Cutevent), the master event manager 106 receives (718) an “Event Ended” orequivalent transaction from the ALC manager 108 and sets (720) theutility to a logical “Not Managed” state. The master event manager 106then notifies (722) each customer that has chosen to receive anotification (e.g., through transmission of an email or otherpre-established notification mechanism) that the power management eventhas ended. Finally, the master event manager 106 sends an “Event Ended”or equivalent transaction message or command to the power savingsapplication 120 and the utility control center 200 (via the UCC commandprocessor 104).

Turning now to FIG. 7, exemplary operational flow diagram 800illustrates steps executed by the ALD server 100 (e.g., as part of theALC manager 108) to manage power consumption in the exemplary power loadmanagement system 10, in accordance with one embodiment of the presentinvention. The steps of FIG. 7 are preferably implemented as a set ofcomputer instructions (software) stored in a memory of the ALD server100 and executed by one or more processors of the ALD server 100. Inaccordance with the logic flow, the ALC manager 108 tracks (802) thestate of each managed active load client 300 by receiving messages,periodically or responsive to polls issued by the ALC manager 108, fromevery active load client 300 that the ALC manager 108 manages. Thesemessages indicate the present states of the active load clients 300. Thestate includes the present consumption of power for each controllabledevice 402-412, 420 controlled by the active load client 300 (or thetotal power consumption for all controllable devices 402-412, 420controlled by the active load client 300 if individual device meteringis not available) and the status of each device 402-412, 420 (e.g.,either “Off” or “On”). The ALC manager 108 stores or logs (804) thepower consumption and device status information in the ALD database 124in a record corresponding to the specified active load client 300 andits associated customer and serving utility.

When the ALC manager 108 receives (806) a transaction message from themaster event manager 106, the ALC manager 108 first determines (808) thetype of transaction received. If the ALC manager 108 receives a “Cut” orequivalent transaction message or command from the master event manager106, the ALC manager 108 enters (810) a “Manage” logical state. The ALCmanager 108 then determines (812) which active load clients 300 andassociated devices 402-412, 420 operating on the utility specified inthe “Cut” message to switch to the “Off” state. If a location (e.g.,list of GPS coordinates, a GPS coordinate range, a geographic area, or apower grid reference area) is included in the “Cut” transaction message,only those active load clients 300 within the specified location areselected for switching to the “Off” state. In other words, the ALCmanager 108 selects the group of active load client devices 300 to whichthe issue a “Turn Off” transaction message based at least partially onthe geographic location of each active load client 300 as such locationrelates to any location identified in the received “Cut” transactionmessage. The ALD database 124 contains information on the present powerconsumption (and/or the average power consumption) for each controllabledevice 402-412, 420 connected to each active load client 300 in thesystem 10. The ALC manager 108 utilizes the stored power consumptioninformation to determine how many, and to select which, devices 402-412,420 to turn off to achieve the power reduction required by the “Cut”message. The ALC manager 108 then sends (814) a “Turn Off” or equivalenttransaction message or command to each active load client 300, alongwith a list of the devices to be turned off and a “change state to off”indication for each device 402-412, 420 in the list. The ALC manager 108then logs (816) the amount of power (either actual or average), asdetermined from the ALD database 124, saved for each active load client300, along with a time stamp indicating when the power was reduced. TheALC manager 108 then schedules (818) transactions for itself to “TurnOn” each turned-off device after a predetermined period of time (e.g.,which may have been set from a utility specified default, set byinstructions from the customer, or otherwise programmed into the ALCmanager 108).

Returning back to block 808, when the ALC manager 108 receives a “TurnOn” or equivalent transaction message or command from the master eventmanager 106 for a specified active load client 300, and the ALCmanager's state is currently in a “Manage” state, the ALC manager 108finds (820) one or more active load clients 300 that are in the “On”state and do not have any of their managed devices 402-412, 420 turnedoff (and are in the specified location if so required by the original“Cut” transaction message), which, when one or more of such devices402-412, 420 are turned off, will save the same or substantially thesame amount of power that is presently being saved by the specifiedactive load clients that are in the “Off” state. Upon identifying newactive load clients 300 from which to save power, the ALC manager 108sends (822) a “Turn Off” or equivalent transaction message or command toeach active load client 300 that must be turned off in order to save thesame amount of power as the active load client(s) to be turned on (i.e.to have its or their managed devices 402-412, 420 turned on) or to savean otherwise acceptable amount of power (e.g., a portion of the powerpreviously saved by the active load client(s) to be turned back on). TheALC manager 108 also sends (824) a “Turn On” or equivalent transactionmessage or command to each active load client 300 to be turned back on.The “Turn On” message instructs all active load clients 300 to which themessage was directed to turn on any controllable devices that have beenturned off, and causes the affected active load clients 300 to instructtheir controllable devices 402-412, 420 to enable the flow of electricpower to their associated power consuming devices (e.g., appliance, HVACunit, and so forth). Finally, the ALC manager 108 logs (826) the timethat the “Turn On” transaction message is sent in the ALD database 124.

Returning once again to block 808, when the ALC manager 108 receives an“End Event” or equivalent transaction message or command from the masterevent manager 106, the ALC manager 108 sends (828) a “Turn On” orequivalent transaction message or command to every active load client300 which is currently in the “Off” state and is served by the servingutility identified in the “End Event” message or to which the “EndEvent” message relates. Upon determining (830) that all the appropriateactive load clients 300 have transitioned to the “On” state, the ALCmanager 108 sends (832) an “Event Ended” or equivalent transactionmessage or command to the master event manager 106.

Referring now to FIG. 8, exemplary operational flow diagram 900illustrates steps executed by the ALD server 100 (e.g., throughoperation of the power savings application 120) to calculate andallocate power savings in the power load management system 10, inaccordance with one embodiment of the present invention. The powersavings application 120 calculates the total amount of power saved byeach utility for each Cut event and the amount of power saved by eachcustomer possessing an active load client 300.

According to the logic flow of FIG. 9, the power savings application 120receives (902) an “Event Ended” or equivalent transaction message orcommand from the master event manager 106 each time a “Cut” or powersavings event has ended. The power savings application 120 then accesses(904) the ALD database 124 for each active load client 300 involved inthe “Cut” event. The database record for each active load client 300contains the actual amount (or average amount) of power that would havebeen used by the active load client 300 during the last “Cut” event,along with the amount of time that each controllable device 402-412, 420associated with the active load client 300 was turned off. The powersavings application 120 uses this information to calculate the amount ofpower (e.g., in megawatts per hour) that was saved for each active loadclient 300. The total power savings for each active load client 300 isstored in its corresponding entry in the ALD database 124. A runningtotal of power saved is kept for each “Cut” transaction. Each utilitythat is served by the ALD server 100 has an entry in the utility P&Cdatabase 134. The power savings application 120 stores (906) the totalamount of power (e.g., in megawatts per hour) saved for the specificutility in the utility's corresponding entry in the utility P&C database134, along with other information related to the power savings event(e.g., the time duration of the event, the number of active load clientsrequired to reach the power savings, average length of time each devicewas in the off state, plus any other information that would be useful infine tuning future events and in improving customer experience). Whenall active load client entries have been processed, the power savingsapplication 120 optionally invokes (908) the carbon savings application132 or, analogously, a sulfur dioxide savings application or a nitrogendioxide savings application, to correlate the power savings with carboncredits, sulfur dioxide credits or nitrogen dioxide credits,respectively, based on the geographic locations of the particularserving utility and customer. Additionally, in one embodiment, thecarbon savings application 132 determines carbon credits based ongovernment approved or supplied formulas and stores the determinedcarbon credits on a per customer and/or per utility basis.

As described above, the present invention encompasses a method formanaging and distributing power within a power management system basedon real-time feedback from addressable and remotely controllable devicesincluding the actual amount of power currently being individually orcollectively consumed by the addressable devices. With this invention, apower management system may pinpoint specific areas of high power usageand more accurately distribute power loads to utilities in need.Additionally, the present invention provides optional participationincentives for customers based on the amount of their actualparticipation in the power management system.

In the foregoing specification, the present invention has been describedwith reference to specific embodiments. However, one of ordinary skillin the art will appreciate that various modifications and changes may bemade without departing from the spirit and scope of the presentinvention as set forth in the appended claims. For example, the presentinvention is applicable for managing the distribution of power fromutility companies to subscribing customers using any number of IP-basedor other communication methods. Additionally, the functions of specificmodules within the ALD server 100 and/or active load client 300 may beperformed by one or more equivalent means. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense, and all such modifications are intended to beincluded within the scope of the present invention.

Benefits, other advantages, and solutions to problems have beendescribed above with regard to specific embodiments of the presentinvention. However, the benefits, advantages, solutions to problems, andany element(s) that may cause or result in such benefits, advantages, orsolutions to become more pronounced are not to be construed as acritical, required, or essential feature or element of any or all theclaims. The invention is defined solely by the appended claims includingany amendments made during the pendency of this application and allequivalents of those claims as issued.

1. A system for managing consumption of power supplied by an electricutility to a plurality of power consuming devices, the systemcomprising: one or more client devices, each client device operating atleast partially responsive to received power control messages andincluding: at least one controllable device interface facilitatingcommunication of power control instructions to at least one controllabledevice, each controllable device selectively enabling and disabling aflow of electric power to a power consuming device of the plurality ofpower consuming devices responsive to the power control instructions;and a device control manager operably coupled to the at least onecontrolled device interface, the device control manager generating thepower control instructions responsive to the received power controlmessages; and a server communicatively coupled to the electric utilityand the one or more client devices, the server including: a commandprocessor operable to receive power control commands from the electricutility and issue power control event messages responsive thereto, atleast one of the power control commands requiring a reduction in anamount of electric power consumed by the plurality of power consumingdevices; an event manager operable to receive the power control eventmessages, maintain at least one power management status relating to eachclient device and issue power control event instructions responsive tothe power control event messages; a database for storing, on a perclient device basis, information relating to power consumed by theplurality of power consuming devices during operation of the pluralityof power consuming devices; and a client device manager operably coupledto the event manager and the database, the client device managerselecting from the database, based on the information stored in thedatabase, at least one client device to which to issue a power controlmessage indicating at least one of an amount of electric power to bereduced and identification of at least one controllable device to beinstructed to disable a flow of electric power to one or more associatedpower consuming devices responsive to receipt of a power control eventinstruction requiring a reduction in a specified amount of electricpower.
 2. The system of claim 1, wherein the client device managerreceives from each client device at least one power consumptionindicator and at least one power management status.
 3. The system ofclaim 2, wherein the at least one power consumption indicator includes apower consumption indicator associated with each controllable device andwherein the at least one power management status includes a powermanagement status associated with each controllable device.
 4. Thesystem of claim 1, wherein the database further includes information, ona per controllable device basis, relating to a maximum amount of timeduring which flow of electric power may be disabled by a particularcontrollable device.
 5. The system of claim 1, wherein the databasefurther includes information, on a per client device basis, relating toa maximum amount of time during which flow of electric power may bedisabled by the at least one controllable device.
 6. The system of claim1, wherein the server further includes a power savings application thatcomputes an amount of electric power saved for each customerparticipating in the system during a power reduction event affecting thecustomer.
 7. The system of claim 1, wherein the server further includesa client interface that facilitates communication of the power controlmessages to the one or more client devices and wherein each clientdevice further includes a communications interface that facilitatescommunication of the power control messages to the client device.
 8. Thesystem of claim 7, wherein the client interface and the communicationsinterface comprise WiMax interfaces.
 9. The system of claim 1, whereinthe at least one controllable device includes at least one smartappliance and wherein at least some of the one or more client devicesfurther include a smart device interface that facilitates communicationof the power control instructions to the at least one smart appliance.10. The system of claim 9, wherein the smart device interface comprisesa broadband overpower line interface.
 11. A server for use in a systemthat manages consumption of power supplied by at least one electricutility to a plurality of power consuming devices, wherein power flow tothe plurality of power consuming devices is enabled and disabled by aplurality of controllable devices and wherein the plurality ofcontrollable devices operated under the control of one or more clientdevices, the server comprising: a command processor operable to receivepower control commands from the at least one electric utility and issuepower control event messages responsive thereto, at least one of thepower control commands requiring a reduction in an amount of electricpower consumed by the plurality of power consuming devices; an eventmanager operable to receive the power control event messages, maintainat least one power management status relating to each client device andissue power control event instructions responsive to the power controlevent messages; a database for storing, on at least one of a per clientdevice basis and a per electric utility basis, information relating topower consumed by the plurality of power consuming devices duringoperation of the plurality of power consuming devices; and a clientdevice manager operably coupled to the event manager and the database,the client device manager selecting from the database, based on theinformation stored in the database, at least one client device to whichto issue a power control message indicating at least one of an amount ofelectric power to be reduced and identification of at least onecontrollable device to be instructed to disable a flow of electric powerto one or more associated power consuming devices responsive to receiptof a power control event instruction requiring a reduction in aspecified amount of electric power.
 12. The server of claim 11, whereinthe power control commands include a power inquiry command requestingthe server to determine an amount of electric power available fortemporary reduction from supply by a requesting electric utility andwherein the command processor issues an associated power control eventmessage responsive to the power inquiry command, the server furthercomprising: a utility database that stores current power usageinformation for the at least one electric utility, wherein the eventmanager accesses the utility database responsive to receipt of theassociated power control event message and communicates a response tothe power inquiry command indicating the amount of power available fortemporary reduction based on the current power usage information.
 13. Aclient device for use in a system that manages consumption of powersupplied by an electric utility to a plurality of power consumingdevices, wherein power flow to at least some of the plurality of powerconsuming devices is enabled and disabled by a plurality of controllabledevices, wherein at least one controllable device operates under thecontrol of the client device, and wherein the client device receivespower control messages from a remote server, the client devicecomprising: at least one controllable device interface facilitatingcommunication of power control instructions to the at least onecontrollable device, the power control instructions causing the at leastone controllable device to selectively enable and disable a flow ofelectric power to a power consuming device of the plurality of powerconsuming devices; and a device control manager operably coupled to theat least one controllable device interface, the device control managergenerating the power control instructions responsive to the receivedpower control messages.
 14. A method for a server to manage a flow ofpower supplied by at least one electric utility to a plurality of powerconsuming devices, the method comprising: receiving a power controlcommand from an electric utility, the power control command requiring areduction in an amount of electric power consumed by at least some ofthe power consuming devices; responsive to the power control command,determining a group of client devices to which to issue a power controlmessage, each client device of the group controlling at least onecontrollable device, each controllable device selectively enabling anddisabling a flow of electric power to at least one power consumingdevice of the plurality of power consuming devices, the power controlmessage indicating at least one of an amount of electric power to bereduced and an identification of one or more controllable devices to beinstructed to disable a flow of electric power to one or more associatedpower consuming devices; and issuing the power control message to the atleast one client device.
 15. The method of claim 14, further comprising:determining an amount of power saved by the electric utility as a resultof issuance of the power control message; and storing an indication ofthe amount of power saved by the electric utility.
 16. The method ofclaim 15, further comprising: correlating the amount of power saved toat least one of an amount of carbon credits, an amount of nitrogendioxide credits, and an amount sulfur dioxide credits based at least ona location of the electric utility.
 17. The method of claim 15, furthercomprising: determining an amount of power saved by each user of aclient device to which the power control message was issued; storing anindication of the amount of power saved by each user; and providing areward incentive to the user based on the amount of power saved over aperiod of time.
 18. The method of claim 15, further comprising:receiving a report message from a first client device of the group, thereport message including an indication of an amount of power consumed byat least a first power consuming device; storing the indication inassociation with a user of the first client device; and using theindication to determine the group of client devices to which to issuethe power control message.
 19. The method of claim 14, furthercomprising: receiving a power inquiry command from the electric utility,the power inquiry command requesting an indication of an amount of powerthat can be at least temporarily reduced from a supply of power providedby the electric utility; determining the amount of power that can be atleast temporarily reduced based on current usage information for theelectric utility; and reporting the indication of the amount of powerthat can be at least temporarily reduced to the electric utility. 20.The method of claim 14, further comprising: receiving a status messagefrom each client device of the group, the status message indicating anoperational status of the client device and power consumptioninformation for each power consuming device controlled by the clientdevice; and storing the status and the power consumption information foruse in determining the group of client devices to which to issue thepower control message.
 21. The method of claim 14, further comprising:receiving a status message from each client device of the group, thestatus message indicating an operational status of the client device andcumulative power consumption information for all power consuming devicescontrolled by the client device; and storing the status and the powerconsumption information for use in determining the group of clientdevices to which to issue the power control message.
 22. The method ofclaim 14, wherein the power control message includes Internet Protocoladdresses of the one or more controllable devices to be instructed todisable a flow of electric power to one or more associated powerconsuming devices.
 23. A method for a client device to manage a flow ofpower supplied by an electric utility to a plurality of power consumingdevices, the client device being responsive to power control messagesissued by a load management server and controlling one or morecontrollable devices that selectively enable and disable a flow ofelectric power to at least some of the plurality of power consumingdevices, the method comprising: receiving a first power control messagefrom the load management server, the first power control messageindicating at least one of an amount of electric power to be reduced andan identification of at least one controllable device to be instructedto disable a flow of electric power to one or more associated powerconsuming devices; and responsive to the first power control message,issuing a power management command to a controllable device causing thecontrollable device to disable a flow of electric power to at least oneassociated power consuming device.
 24. The method of claim 23, whereinthe first power control message is encrypted, the method furthercomprising: decrypting the first power control message responsive toreceiving the first power control message.
 25. The method of claim 23,further comprising: communicating a report message to the loadmanagement server, the report message including an indication of anamount of power consumed by at least a first power consuming device.